Outdoor lighting fixtures control systems and methods

ABSTRACT

One embodiment of the invention relates to a system for operating a plurality of streetlights in response to motion from a vehicle. The system includes a sensor associated with at least one of the streetlights and configured to detect the presence of a moving vehicle and to provide a signal representative of the moving vehicle. The system further includes a radio frequency transceiver associated with each of the streetlights. The system yet further includes processing electronics configured to receive the signal representative of the moving vehicle from the sensor and to cause the radio frequency transceiver to transmit a command to one or more of the plurality of the streetlights to change lighting states along a pathway for the vehicle.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application is a continuation of U.S. application Ser. No.13/932,962, filed Jul. 1, 2013, which is a Divisional of U.S.application Ser. No. 13/223,146, filed Aug. 31, 2011; U.S. applicationSer. No. 13/223,146, filed Aug. 31, 2011 claims the benefit of priorityunder 35 U.S.C. § 119(e) of U.S. Provisional Application No. 61/380,165,filed on Sep. 3, 2010, and titled “Outdoor Lighting Fixtures ControlSystems and Methods.” U.S. application Ser. No. 13/223,146, filed Aug.31, 2011 also claims the benefit of priority as a Continuation-In-Partof U.S. application Ser. No. 12/875,930, filed on Sep. 3, 2010, whichclaims the benefit of priority of U.S. Application No. 61/275,985, filedon Sep. 4, 2009. U.S. application Ser. No. 13/223,146, filed Aug. 31,2011 also claims the benefit of priority as a Continuation-In-Part ofU.S. application Ser. No. 12/550,270, filed on Aug. 28, 2009, which is aContinuation-In-Part of application Ser. No. 11/771,317, filed Jun. 29,2007, and is also a Continuation-In-Part of U.S. Ser. No. 12/240,805,filed on Sep. 29, 2008, which is a Continuation-In-Part of U.S.application Ser. No. 12/057,217, filed Mar. 27, 2008. The subject matterof application Ser. Nos. 13/932,962, 13/223,146, 61/380,128, 61/275,985,12/875,930, 12/550,270, 12/240,805, 12/057,217, and 11/771,317 arehereby incorporated herein by reference in their entirety.

BACKGROUND

The present invention relates generally to the field of outdoor lightingsystems. The present invention more particularly relates to the field ofoutdoor lighting systems for illuminating streets.

Outdoor lights, such as street lights, can provide beneficialillumination throughout dusk, the night, and during early morning hours.Conventional outdoor lights remain fully lit regardless of whether anypeople or cars are nearby. Applicants have identified the need forimproved outdoor lighting control systems and methods for saving energyand reducing the amount of light pollution provided by outdoor lights.

SUMMARY

One embodiment of the invention relates to a system for operating aplurality of streetlights in response to motion from a vehicle. Thesystem includes a sensor associated with at least one of thestreetlights and configured to detect the presence of a moving vehicleand to provide a signal representative of the moving vehicle. The systemfurther includes a radio frequency transceiver associated with each ofthe streetlights. The system yet further includes processing electronicsconfigured to receive the signal representative of the moving vehiclefrom the sensor and to cause the radio frequency transceiver to transmita command to one or more of the plurality of the streetlights to changelighting states along a pathway for the vehicle. The sensor can detectsa speed of the moving vehicle and streetlights in the pathway can beilluminated in a sequence that is at least as fast as the speed of thevehicle. The sensor can also or alternatively detect a direction of themoving vehicle relative to the pathway. Once activated, the streetlightscan remain on for a predetermined period of time and then deactivateupon expiration of the predetermined period of time, reilluminating whenthe sensor detects the presence of another moving vehicle. The pluralityof streetlights can be organized into zones and one or more of the zonesmay be completely or at least partially activated to illuminate thepathway. The streetlights can be high intensity discharge fluorescentlamps. The pathway can be a street, streets, a parking lot, a portion ofa parking lot, or another pathway along which a vehicle travels.

One embodiment of the invention relates to a system for illuminating anoutdoor area. The system includes a first outdoor lighting fixture and afirst control circuit for the first outdoor lighting fixture. The systemfurther includes a first radio frequency transceiver coupled to thecontrol circuit via a wired communications link. The system yet furtherincludes a sensor associated with the first outdoor lighting fixture andconfigured to provide a sensor output to the control circuit for thefirst outdoor light. The system also includes a second outdoor lightingfixture. The control circuit is configured to cause the first radiofrequency transceiver to send data to the second outdoor lightingfixture in response to the sensor output. The second outdoor lightingfixture includes a second control circuit configured to use the datasent by the first radio frequency transceiver to determine whether tochange lighting states.

Another embodiment of the invention relates to a method for illuminatingan outdoor area. The method includes sensing motion using a sensor and acoupled control circuit and using the control circuit to cause a radiofrequency transceiver to transmit a command to at least one lightingfixture. The method further includes receiving the command at the atleast one lighting fixture and using processing electronics of the atleast one lighting fixture to cause the at least one lighting fixture tochange lighting states.

Another embodiment of the invention relates to a lighting fixture. Thelighting fixture includes a first ballast for illuminating a first lightand a second ballast for illuminating a second light. The lightingfixture further includes a motion sensor, a radio frequency transceiver,and a circuit coupled to the first ballast, the second ballast, themotion sensor, and the radio frequency transceiver. The circuit isconfigured to cause the first ballast to be in an activated state ofoperation such that the first light is illuminating and the secondballast to be in a deactivated state of operation such that the secondlight is not illuminated. The circuit is further configured to receive asignal from the motion sensor and to determine whether the signal isrepresentative of motion. The circuit is yet further configured torespond to a determination that the signal is representative of motionby causing the second ballast to enter an activated state of operationsuch that the second light is illuminated. The circuit is furtherconfigured to cause the radio frequency transceiver to transmit at leastone of a message indicating motion and an illuminate command for receiptby other lighting fixtures.

Another embodiment of the invention relates to a control device for aplurality of outdoor lighting fixtures. The control device includes asensor and a radio frequency transceiver. The control device furtherincludes processing electronics configured to receive a sensor inputfrom the sensor and to cause the radio frequency transceiver to, inresponse to the sensor input, transmit a command to the plurality ofoutdoor lighting fixtures to change lighting states.

Alternative exemplary embodiments relate to other features andcombinations of features as may be generally recited in the claims.

BRIEF DESCRIPTION OF THE FIGURES

The disclosure will become more fully understood from the followingdetailed description, taken in conjunction with the accompanyingfigures, wherein like reference numerals refer to like elements, inwhich:

FIG. 1 is a bottom perspective view of an outdoor fluorescent lightingfixture system, according to an exemplary embodiment;

FIG. 2 is an illustration of a system for illuminating an outdoor areausing multiple of the lighting fixtures of FIG. 1, according to anexemplary embodiment;

FIG. 3A is a diagram of a system for controlling a street light of thesystem of FIG. 2, according to an exemplary embodiment;

FIG. 3B is a block diagram of the controller and circuit of the systemof FIG. 3A, according to an exemplary embodiment;

FIG. 4A is a flow chart of a process for illuminating a system ofoutdoor lighting fixtures, according to an exemplary embodiment;

FIG. 4B is a flow chart of a process for using motion information tochange states of a system of outdoor lighting fixtures, according to anexemplary embodiment;

FIG. 5A is a more detailed block diagram of the master controller ofFIG. 3A, according to an exemplary embodiment; and

FIG. 5B is a diagram of a facility lighting system for use with thesystems and methods of the present disclosure, according to an exemplaryembodiment.

DETAILED DESCRIPTION

Referring generally to the Figures, one or more control devices are usedto provide lighting commands or information to a plurality of outdoorlighting fixtures. The control device includes a sensor, a radiofrequency transceiver, and processing electronics. The processingelectronics are configured to receive sensor inputs from the sensor andto cause the radio frequency transceiver to transmit a command to theplurality of outdoor lighting fixtures in response to the sensor inputs.The outdoor lights that receive the command may be configured to changefrom a dimmed (e.g., partially illuminated, illuminated at partialintensity, “off” or not at all illuminated, etc.) lighting state to abrighter (e.g., fully illuminated, more illuminated, “on”, etc.)lighting state. The sensor may be a motion sensor or a camera configuredto detect the motion of a vehicle or a person. The processingelectronics effectively “blasts” (i.e., transmits, broadcasts) radiofrequency communications that announce the presence of the detectedmotion to other nearby lights. For example, if a sensor detects motionon a street due to a car driving down the street, the control device canuse the detection of motion to blast a “lights on” command down thestreet in advance of the car, creating an effect whereby the road infront of the car illuminates. Such a control device and outdoor lightingfixture system can advantageously provide energy savings for streetlights and other outdoor or lighting systems (e.g., parking lot systems,garage systems, warehouses, gas station canopy lights, rural roadways,highways, etc.) relative to similar systems where the lights are fullyilluminated at all times or during all “lighting” hours. The energysavings may be particularly great in rural or remote areas wherelighting is desired when the streets are populated but unnecessary for alarge percentage of the time.

In some exemplary embodiments the lights can revert back to a dimmed oroff state if no motion occurs within a predetermined amount of time. Insome embodiments multiple of the outdoor lighting fixtures may include amotion sensor or camera and one or more of the outdoor lightingfixtures' control circuits may be configured to use timing betweensensed motion to determine the speed of the moving object (e.g., howfast a car is driving down a street). The control circuit or circuitscan blast lighting commands forward at a speed that is sufficient toprovide a good visible range of lighting for nighttime driving at thesensed speed.

In yet other embodiments, a city or outdoor area may be divided into aplurality of zones. Outdoor lighting fixtures within the zone may beassigned a zone identifier. Whenever motion is detected within a zone,the controller coupled to the detecting sensor can transmit a signal tothe other outdoor lighting fixtures in the zone with “on” lighting statecommand. The signal may include a representation of the zone forcomparison by the receiving lighting fixtures to their zone identifiers.In such embodiments, an entire lighting zone may be configured to turnon or intensify the lighting if any motion is detected within the zone.A computer control system may be configured to transmit configurationinformation to the outdoor lighting fixtures and may be configured toprovide graphical user interfaces for receiving user selections for usein the configuration. These graphical user interfaces may allow a userto assign zone identifiers to individual outdoor lighting fixtures,assign zones identifiers to different groups of outdoor lightingfixtures, reconfigure zone boundaries, and to configured the logic forthe outdoor lighting fixtures of a zone. For example, the graphical userinterface may provide controls for allowing a user to instruct thelighting fixtures in a zone to turn on based not only on motion withintheir zone, but also to turn on based on “motion” messages from adjacentzones.

Referring now to FIG. 1, a bottom perspective view of an outdoorfluorescent lighting fixture system is shown, according to an exemplaryembodiment. The outdoor fluorescent lighting fixture of FIG. 1 isconfigured for applications such as a street lighting application orparking lot lighting application. In some embodiments, the outdoorfluorescent lighting fixture is configured to include a mounting systemfor coupling the fluorescent lighting fixture to high poles or masts.The outdoor fluorescent lighting fixture may also be configured toprovide wired or wireless communications capabilities, one or morecontrol algorithms (e.g., based on sensor feedback, received wirelesscommands or wireless messages, etc.), built-in redundancy, and venting.Many of the outdoor lighting fixtures described herein mayadvantageously mount to existing street light poles or other outdoorstructures for holding lighting fixtures such that no modification tothe existing infrastructure (other than replacing the lighting fixtureitself) is necessary. In some embodiments, the outdoor lighting fixturesinclude control circuits for providing energy saving control features toa group of lighting fixtures or a municipality without changing existingpower wiring run from pole to pole.

In FIG. 1, outdoor lighting fixture 10 is configured for coupling to apole and for directing light generally toward the ground. Such anorientation may be used to illuminate streets, sidewalks, bridges,parking lots, and other outdoor areas where ground illumination isdesirable. Outdoor lighting fixture 10 is shown to include a mountingsystem 32 and a housing 30 (e.g., fluorescent tubes) and includes a lens(e.g., a plastic sheet, a glass sheet, etc.) that allows light from theone or more fluorescent lamps 12 to be provided from housing 30.

Mounting system 32 is shown to include a mount 34 and a compressionsleeve 36. Compression sleeve 36 is configured to receive the pole andto tighten around the pole (e.g., when a clamp is closed, when a bolt istightened, etc.). Compression sleeve 36 may be sized and shaped forattachment to existing outdoor poles such as street light poles,sidewalk poles, parking lot poles, and the like. As is provided bymounting system 32, the coupling mechanism may be mechanically adaptableto different poles or masts. For example, compression sleeve 36 mayinclude a taper or a tapered cut so that compression sleeve 36 need notmatch the exact diameter of the pole or mast to which it will becoupled. While lighting fixture 10 shown in FIG. 1 utilizes acompression sleeve 36 for the mechanism for coupling the mounting systemto a pole or mast, other coupling mechanisms may alternatively be used(e.g., a two-piece clamp, one or more arms that bolt to the pole, etc.).

According to an exemplary embodiment, fixture 10 and housing 30 areelongated and mount 34 extends along the length of housing 30. Mount 34is preferably secured to housing 30 in at least one location beyond alengthwise center point and at least one location before the lengthwisecenter point. In other exemplary embodiments, the axis of compressionsleeve 36 also extends along the length of housing 30. In the embodimentshown in FIG. 1, compression sleeve 36 is coupled to one end of mount 34near a lengthwise end of housing 30.

Housing 30 is shown to include a fixture pan 50 and a door frame 52 thatmates with fixture pan 50. In the embodiments shown in the Figures, doorframe 52 is mounted to fixture pan 50 via hinges 54 and latches 56. Whenlatches 56 are released, door frame 52 swings away from fixture pan 50to allow access to fluorescent lamps 12 within housing 30. Latches 56are shown as compression-type latches, although many alternative lockingor latching mechanisms may be alternatively or additionally provided tosecure the different sections of the housing. In some embodiments thelatches may be similar to those found on “NEMA 4” type junction boxes orother closures. Further, many different hinge mechanisms may be used.Yet further, in some embodiments door frame 52 and fixture pan 50 maynot be joined by a hinge and may be secured together via latches 56 onall sides, any number of screws, bolts or other fasteners that do notallow hinging, or the like. In an exemplary embodiment, fixture pan 50and door frame 52 are configured to sandwich a rubber gasket thatprovides some sealing of the interior of housing 30 from the outsideenvironment. In some embodiments the entirety of the interior oflighting fixture 10 is sealed such that rain and other environmentalmoisture does not easily enter housing 30. Housing 30 and its componentpieces may be galvanized steel but may be any other metal (e.g.,aluminum), plastic, and/or composite material. Housing 30, mountingsystem 32 and/or the other metal structures of lighting fixture 10 maybe powder coated or otherwise treated for durability of the metal.According to an exemplary embodiment housing 30 is powder coated on theinterior and exterior surfaces to provide a hard, relatively abrasionresistant, and tough surface finish.

Housing 30, mounting system 32, compression sleeve 36, and the entiretyof lighting fixture 10 are preferably extremely robust and able towithstand environmental abuses of outdoor lighting fixtures. The shapeof housing 30 and mounting system 32 are preferably such that theeffective projection area (EPA) relative to strong horizontal winds isminimized—which correspondingly provides for minimized wind loadingparameters of the lighting fixture.

Ballasts, structures for holding lamps, and the lamps themselves may beinstalled to the interior of fixture pan 50. Further, a reflector may beinstalled between the lamp and the interior metal of fixture pan 50. Thereflector may be of a defined geometry and coated with a whitereflective thermosetting powder coating applied to the light reflectingside of the body (i.e., a side of the reflector body that faces toward afluorescent light bulb). The white reflective coating may havereflective properties, which in combination with the defined geometry ofthe reflector, provides high reflectivity. The reflective coating may beas described in U.S. Prov. Pat. App. No. 61/165,397, filed Mar. 31,2009. In other exemplary embodiments, different reflector geometries maybe used and the reflector may be uncoated or coated with other coatingmaterials. In yet other embodiments, the reflector may be a “MIRO 4”type reflector manufactured and sold by Alanod GmbH & Co KG.

The shape and orientation of housing 30 relative to the reflector and/orthe lamps is configured to provide a substantially full cut off suchthat light does not project above the plane of fixture pan 50. Thelighting fixtures described herein are preferably “dark-sky” compliantor friendly.

To provide further resistance to environmental variables such asmoisture, housing 30 may include one or more vents configured to allowmoisture and air to escape housing 30 while not allowing moisture toenter housing 30. Moisture may enter enclosed lighting fixtures due tovacuums that can form during hot/cold cycling of the lamps. According toan exemplary embodiment, the vents include, are covered by, or are infront of one or more pieces of material that provide oleophobic andhydrophobic protection from water, washing products, dirt, dust andother air contaminants. According to an exemplary embodiment the ventsmay include GORE membrane sold and manufactured by W.L. Gore &Associates, Inc. The vent may include a hole in the body of housing 30that is plugged with a snap-fit (or otherwise fit) plug including anexpanded polytetrafluoroethylene (ePTFE) membrane with a polyesternon-woven backing material.

The lighting fixture system includes a controller 46. Controller 46 isconnected to lighting fixture 10 via wire 44. Controller 46 isconfigured to control the switching between different states of lightingfixture 10 (e.g., all lamps on, all lamps off, some lamps on, etc.).

According to various embodiments, controller 46 is further configured tolog usage information for lighting fixture 10 in a memory device localto controller 46. Controller 46 may further be configured to use thelogged usage information to affect control logic of controller 46.Controller 46 may also or alternatively be configured to provide thelogged usage information to another device for processing, storage, ordisplay. Controller 46 is shown to include a sensor 43 coupled tocontroller 46 (e.g., controller 46's exterior housing). Controller 46may be configured to use signals received from sensor 43 to affectcontrol logic of controller 46. Further, controller 46 may be configuredto provide information relating to sensor 43 to another device.

While various Figures of the present disclosure, including FIG. 1,illustrate lighting fixtures for fluorescent lamps, it should be notedthat embodiments of the present disclosure may be utilized with any typeof lighting fixture and/or lamps. Further, while housing 30 is shown asbeing fully enclosed (e.g., having a door and window covering theunderside of the fixture), it should be noted that any variety oflighting fixture shapes, styles, or types may be utilized withembodiments of the present disclosure. Further, while controller 46 isshown as having a housing that is exterior to housing 30 of lightingfixture 10, it should be appreciated that controller 46 may bephysically integrated with housing 30. For example, one or more circuitboards or circuit elements of controller 46 may be housed within, on topof, or otherwise secured to housing 30. Further, in other exemplaryembodiments, controller 46 (including its housing) may be coupleddirectly to housing 30. For example, controller 46's housing may belatched, bolted, clipped, or otherwise coupled to the interior orexterior of housing 30. Controller 46's housing may generally be shapedas a rectangle (as shown), may include one or more non-right angles orcurves, or otherwise configured. In an exemplary embodiment, controller46's housing is made of plastic and housing 30 for lighting fixture 10is made from metal. In other embodiments, other suitable materials maybe used.

Referring still to FIG. 1, lighting fixture 10 includes antennas 40which are coupled to radio frequency transceiver circuitry contained inlighting fixture 10. In alternative embodiments antennas 40 are locatedon controller 46 and controller 46 is held above, below, or laterallyrelative to outdoor lighting fixture 10 on the pole or mast to whichoutdoor lighting fixture 10 is coupled. In the embodiment shown in FIG.1, antennas 40 are coupled to the top of mounting system 32 and theradio frequency transceiver for antennas 40 is housed within one ofmounting system 32, housing 30, and the housing of controller 46. Whilemultiple antennas for the radio frequency transceiver may be provided tooutdoor lighting fixture 10, in other embodiments only a single antennais coupled to outdoor lighting fixture 10's radio frequency transceiver.According to various embodiments, antennas 40 can be configured tosupport a multiple-input and multiple-out (MIMO) antenna configuration,a single-input and multiple-output antenna configuration (SIMO), amultiple-input and single-output antenna configuration (MISO), asingle-input and single-output antenna configuration (SISO), orotherwise. According to an exemplary embodiment antennas 40 areconfigured (e.g., tuned) to provide 2.4 ghz WiFi communicationscapabilities. In other exemplary embodiments antennas 40 are configured(e.g., tuned, controlled to, etc.) provide 5.8 ghz WiFi communicationscapabilities. In yet other exemplary embodiments other wirelessnetworking protocols, communications capabilities, standards, orproprietary communications schemes may be implemented in outdoorlighting fixture 10 and by antennas 40. Antennas 40 will be shaped,sized, and located appropriately relative to outdoor lighting fixture 10based on the protocols, communications schemes, and other radiofrequency design considerations. In an exemplary embodiment antennas 40are used by a radio frequency transceiver located with lighting fixture10, inside housing 30, or otherwise located to provide a wirelessnetworking access point or “hotspot.” Accordingly, once the radiofrequency transceiver and antennas 40 of lighting fixture 10 are active,users may use laptops, desktops, or portable electronic devices havingradio frequency transceivers to wirelessly communicate with the radiofrequency transceiver and antennas 40 of lighting fixture 10. Using anuplink connection of the radio frequency transceiver (e.g., provided bya wired high speed networking line, provided via a wireless hop toanother device or network, etc.) outdoor lighting fixture 10 can useantennas 40 and the associated radio frequency transceiver to serve as arouter or bridge to, for example, the Internet.

Referring now to FIG. 2, an illustration of a system for illuminating anoutdoor area such as a street is shown, according to an exemplaryembodiment. The system may include multiple zones (e.g., zone 102 or“Zone I” and zone 104 or “Zone II”) and multiple lighting fixtureswithin each zone 102, 104. For example, lighting fixtures 10, 12, 14, 16are in zone 102 and lighting fixtures 18, 20, 22 are in zone 104. Any oflighting fixtures 10-22 may include sensors (e.g., a motion sensor)configured to detect motion. For example, lighting fixture 10 mayinclude a motion sensor for detecting a vehicle approaching zone 102(e.g., vehicle 100).

In the embodiment of FIG. 2, a sensor of fixture 10 may detect vehicle100 approaching zone 102. A radio frequency transceiver of fixture 10may be configured to provide a sensor output related to the detection ofvehicle 100 to the other fixtures 12, 14, 16 of zone 102. For example,in the embodiment of FIG. 2, fixture 10 may provide a wireless datatransmission to fixtures 12, 14 indicating that vehicle 100 is present.Fixtures 12, 14 may use the provided sensor output to determine tochange states from an “off” state to an “on” state. Fixtures 12, 14 mayadditionally provide the sensor output to additional fixtures (e.g.,fixtures 16) such that all lighting fixtures within zone 102 areprovided the sensor output. The lighting fixtures of zone 102 mayadditionally provide the sensor output to zone 104 and any other zones.For example, fixtures 14, 16 may transmit the sensor output to fixtures18, 20 of zone 104, and the sensor output may be transmitted throughoutzone 104 to other lighting fixtures (e.g., fixture 22). Such aconfiguration may allow the lighting fixtures of a particular zone(e.g., zone 102) to turn on when a sensor of one of the lightingfixtures (e.g., fixture 10) detects vehicle 100. Such a configurationmay further allow additional zones (e.g., zone 104 and further zones) toturn on their associated lighting fixtures when a previous zone detectsvehicle 100, before vehicle 100 approaches the zone. According to anexemplary embodiment, the range of how many zones to send the sensoroutput to may depend upon environmental factors (e.g., inclementweather, if it is nighttime, if it is foggy, etc.).

Referring further to FIG. 2, one or more lighting fixtures may receivedata from a remote or local controller. For example, lighting fixture 10may receive data from a master controller either wirelessly, via a wiredconnection, or from a controller within fixture 10, relating tooperation of fixture 10 and all fixtures in zones 102, 104, or otherzones. For example, lighting fixture 10 may receive a command to changeto an “on” state and may transmit the command to other lighting fixturesin zones 102, 104 as a result.

FIG. 3A is a diagram of a system for controlling a lighting fixture 10according to an exemplary embodiment. Lighting fixture 10 includeshousing 30 and mounting system 32 as described in the embodiment ofFIG. 1. Electronics for lighting fixture 10 are shown inside mountingsystem 32. The electronics may be user-accessible via an opening inmounting system 32. The diagram shown in FIG. 3A illustrates two lampsets 340, 342 with two fluorescent lamps forming each lamp set 340, 342.Each lamp set 340, 342 may include one or any number of additionalfluorescent lamps. Further, while some embodiments described hereinrelate to providing redundant lamp sets and ballasts, it should beappreciated that many embodiments of the present disclosure may onlyinclude a single lamp set and a single ballast. In other embodimentsmore than two ballasts and lamp sets may be included in a singlelighting fixture. While the fluorescent lamps are illustrated as tubelamps extending lengthwise relative to the lighting fixture, thefluorescent lamps may be compact fluorescent bulbs, run perpendicular tothe length of the lighting fixture, or be otherwise oriented.

Referring still to FIG. 3A, the fixture mounting system is shown toinclude a control circuit 310 and a radio frequency transceiver 306communicably connected to control circuit 310. Control circuit 310 iscoupled to ballasts 344, 346 and is configured to provide controlsignals to ballasts 344, 346. Control circuit 310 may be coupled to arelay or relays so that control circuit 310 controllably switches therelay from providing power to ballasts 344, 346 or from restrictingpower to ballasts 344, 346. Ballasts 344, 346 may be configured toprovide different lighting (e.g., ballast 344 may be configured forrelatively dim lighting and ballast 346 may be configured for fulllighting). According to an exemplary embodiment, the system shown inFIG. 3A is configured to receive control signals from a mastercontroller 302 or a master transceiver 304 via radio frequencytransceiver 306. In other embodiments the system shown in FIG. 3A isalso configured to provide information to one or more remote sources viaradio frequency transceiver 306.

In an exemplary embodiment radio frequency transceiver 306 is a WiFitransceiver configured to serve as a wireless access point. Outdoorlighting fixture 10 is further shown to include a wired uplink interface311. Wired uplink interface 311 may be or include a wire terminal,hardware for interpreting analog or digital signals received at the wireterminal, or one or more jacks, connectors, plugs, filters, or otherhardware (or software) for receiving and interpreting signals receivedvia the wire 312 from a data communications network 314 (e.g., a remotesource). Radio frequency transceiver 306 may include an encoder, amodulator, an amplifier, a demodulator, a decoder, an antenna, one ormore filters, one or more buffers, one or more logic modules forinterpreting received transmissions, and/or one or more logic modulesfor appropriately formatting transmissions. Fixture 10 is further shownto include antennas 40 as described in FIG. 1. Antennas 40 areconfigured to communicate with subsequent lighting fixtures 330 (e.g.,the “next” lighting fixtures down the street) or other connected devices332.

The circuit shown in FIG. 3A is shown as being entirely enclosed withinmounting system 32 and as a single unit (e.g., single PCB, flexible PCB,separate PCB's but closely coupled). In other embodiments, however, thecircuit may be distributed (e.g., having some components outside ofmounting system 32, having some components within housing 30, etc.).

FIG. 3A is further shown to include an environment sensor 308.Environment sensor 308 is shown coupled to the underside of housing 30.In other embodiments, sensor 308 may be installed at the top of mountingsystem 32, within housing 30, or in any other area of lighting fixture10. In yet other embodiments, environment sensor 308 may be remote fromthe fixture itself (e.g., coupled to a lower location on the pole,coupled to a street sign, coupled to a stop light, etc.). It shouldfurther be mentioned that one environment sensor 308 may serve multiplefixtures. This may be accomplished by environment sensor 308 providingoutput signals to multiple fixtures or by environment sensor 308providing output signals to a single fixture which is configured toforward the signals (or a representation or message derived from thesignals) to other fixtures or to a master controller 302 for action.Environment sensor 308 may be an occupancy sensor, a motion sensor, aphotocell, an infrared sensor, a temperature sensor, or any other typeof sensor for supporting the activities described herein. Controlcircuit 310 coupled to environment sensor 308 may be configured to causelamps 340, 342 to illuminate when movement is detected or based on someother logic determination using sensor input. In an exemplaryembodiment, control circuit 310 may also be configured to cause signalsto be transmitted by radio frequency transceiver 306 to a securitymonitor observed by security personnel. Receipt of these signals maycause a system controlling a pan-tilt-zoom security camera to aim towardthe area covered by a light. The signals (or other alerts) may also besent to other locations such as a police station system for action. Forexample, if activity continues occurring in a parking lot after-hours,as detected by occupancy sensors on a system of lighting fixtures asdescribed herein, the lighting fixtures can each communicate (wired,wirelessly, etc.) this activity to a master controller and the mastercontroller may send a request for inspection to security or police.Control circuit 310 may also be configured to turn the lighting fixtureon for a period of time prior to turning the lighting fixture off if nofurther occupancy is detected.

Referring now to FIG. 3B, a block diagram of a control device 350 andcircuit 310 illustrated in FIG. 3A is shown, according to an exemplaryembodiment. In some embodiments activities of circuit 310 are controlledor facilitated using one or more processors (e.g., a programmableintegrated circuit, a field programmable gate array, an applicationspecific integrated circuit, a general purpose processor, a processorconfigured to execute instructions it receives from memory, etc.). Inother embodiments, activities of circuit 310 are controlled andfacilitated without the use of one or more processors and areimplemented via a circuit of analog and/or digital electronicscomponents. Circuit 310 includes processor 352 and memory 354. Processor352 may be a general purpose processor, a specific purpose processor, aprogrammable logic controller (PLC), a field programmable gate array, acombination thereof, or otherwise and configured to complete, cause thecompletion of, and/or facilitate the completion of the activities ofcircuit 310. Memory 354 of circuit 310 may be computer memory,semiconductor-based, volatile, non-volatile, random access memory, flashmemory, magnetic core memory, or any other suitable memory for storinginformation. Processor 352 may operate to execute computer code storedin memory 354 or in any other logic module of control device 350.Processor 352 may, for example, include computer code for completing thesteps shown in FIG. 4A-B. To complete the steps shown in FIG. 4A,processor 352 may, for example, continuously loop through a timing andinput checking algorithm, load new functions as needed, and communicatewith hardware such as the sensor and the radio frequency transceiver.

The circuit is further shown to include a communications interface(e.g., radio frequency (RF) transceiver 306) and a sensor interface 378.RF transceiver 306 may be integrated with circuit 310 rather than beingseparate. In other embodiments, RF transceiver 306 may be configured tocontrol, drive, or otherwise communicate with the communicationsinterface shown in FIG. 3A. In yet other embodiments, RF transceiver 306may be of a first type and the communications interface shown in FIG. 3Amay be of a second type. For example, RF transceiver 306 may be a wireinterface for communicating with existing municipal street lightcircuits, schedulers, or networks while the communications interface ofFIG. 3A may be a radio frequency transceiver for communicating withother remote sources or networks. In the present disclosure, the termtransceiver may refer to an integrated transmitter and receiver pair ora separate transmitter and receiver.

Sensor interface 378 may be configured to receive signals fromenvironment sensor 308. Sensor interface 378 may include any number ofjacks, terminals, solder points or other connectors for receiving a wireor lead from environment sensor 308. Sensor interface 378 may also oralternatively be a radio frequency transceiver or receiver for receivingsignals from wireless sensors. For example, sensor interface 378 may bea Bluetooth protocol compatible transceiver, a ZigBee transceiver, orany other standard or proprietary transceiver. Regardless of thecommunication medium used, sensor interface 378 may include filters,analog to digital converters, buffers, or other components configured tohandle signals received from environment sensor 308. Sensor interface378 may be configured to provide the result of any signal transformation(or the raw signal) to circuit 310 for further processing.

Circuit 310 is further shown to include a command and control module356, a logging module 358, an end of life module 360, a schedulingmodule 362, a timer 364, an environment processing module 366, andfixture data 368. Using signals received from communications electronicsof the lighting fixture and/or signals received from one or more sensors(e.g., photocells, occupancy sensors, etc.), command and control module356 is configured to control the ballasts and lamps of the fixture.Command and control module 356 may include the primary controlalgorithm/loop for operating the fixture and may call, initiate, passvalues to, receive values from, or otherwise use the other modules ofthe circuit. For example, command and control module 356 may primarilyoperate the fixture using a schedule as described below with respect toscheduling module 362, but may allow upstream or peer control (e.g.,“override control”) to allow a remote source to cause the ballast/lampsto turn on or off. Command and control module 356 may be used to controltwo-way communication using communications electronics of the lightingfixture.

Logging module 358 is configured to identify and store fixture eventinformation. For example, logging module 358 may be configured toidentify (e.g., by receiving a signal from another component of thecircuit) when the lamps of the fixture are being or have been turned offor turned on. These events may be recorded by logging module 358 with adate/time stamp and with any other data. For example, logging module 358may record each event as a row in a two dimensional table (e.g.,implemented as a part of a relational database, implemented as a flatfile stored in memory, etc.) with the fields such as event name, eventdate/time, event cause, event source. One module that may utilize suchinformation is end of life module 360. End of life module 360 may beconfigured to compile a time of use total by querying or otherwiseaggregating the data stored by logging module 358. Events logged by thesystem may be transmitted using the communications interfaces or otherelectronics to a remote source via a wired or wireless connection.Messages transmitting logged events or data may include an identifierunique to the lighting fixture (e.g., lighting fixture's communicationhardware) that identify the fixture specifically. In addition to theactivities of end of life module 360, command and control module 356 maybe configured to cause communications electronics of the fixture totransmit messages from the log or other messages upon identifying afailure (e.g., a power supply failure, a control system failure, aballast failure, a lamp failure, etc.). While logging module 358 may beprimarily used to log on/off events, logging module 358 (or anothermodule of the control system) may log energy draw (or some value derivedfrom energy draw such as a carbon equivalent amount) by the lightingfixture.

FIG. 3B is further shown to include a scheduling module 362. Schedulingmodule 362 may be used by the circuit to determine when the lamps of thelighting fixture should be turned on or off. Scheduling module 362 mayonly consider time, or may also consider inputs received fromenvironment sensor 308 (e.g., indicating that it is night out and thatartificial light is necessary). Scheduling module 362 may access aschedule stored in memory 354 of the circuit to carry out its tasks. Insome embodiments schedule data may be user-updatable via a remote sourceand transmitted to the fixture via the circuit and a communicationsinterface. While end of life module 360 may utilize an actual log offixture events as described in the previous paragraph, in someembodiments end of life module 360 may utilize scheduling information tomake an end of life determination. In yet other embodiments, loggingmodule 358 may receive data from scheduling module 362 to create itslog. Control device 350 and circuit 310 is further shown to include atimer 364 that may be used by circuit 310 to maintain a date/time foruse by or for checking against information of scheduling module 362, endof life module 360, or logging module 358. Environment processing module366 may be configured to process signals received from one or moresensors such as environment sensor 308. Environment processing module366 may be configured to, for example, keep the lamp of the lightingfixture turned off between the hours of one and five A.M. if there is nomovement detected by a nearby environment sensor. In other embodiments,environment processing module 366 may interpret the signals receivedfrom sensors but may not make final fixture behavior determinations. Insuch embodiments, a main logic module for the circuit or logic includedin processor 352 or memory 354 may make the fixture behaviordeterminations using input from, for example, environment processingmodule 366, scheduling module 362, timer 364, and fixture data 368.

Referring further to FIG. 3B, control device 350 includes circuitryconfigured with an algorithm to control on/off cycling of connectedlighting fixtures, an algorithm to log usage information for thelighting fixture, an algorithm configured to prevent premature restrikesto limit wear on the lamps and ballast, and an algorithm configured toallow control device 350 to send and receive commands or informationfrom other peer devices independently from a master controller or mastertransceiver.

Control device 350 is shown to include power relays 380 configured tocontrollably switch on or off high voltage power outputs that may beprovided to first ballast 344 and second ballast 346 of FIG. 3A viawires 381, 382. It should be noted that in other exemplary embodiments,power relays 380 may be configured to provide a low voltage controlsignal, optical signal, or otherwise to the lighting fixture which maycause one or more ballasts, lamps, and/or circuits of the fluorescentlighting fixture that the controller serves to turn on and off. Whilepower relays 380 are configured to provide high voltage power outputs toballasts 344, 346, it should be appreciated that control device 350 mayinclude a port, terminal, receiver, or other input for receiving powerfrom a high voltage power source. In embodiments where a relatively lowvoltage or no voltage control signal is provided by relays 380, powerfor circuitry of control device 350 may be received from a power sourceprovided to the lighting fixtures or from another source. In anyembodiment of control device 350, appropriate power supply circuitry(e.g., filtering circuitry, stabilizing circuitry, etc.) may be includedwith control device 350 to provide power to the components of controldevice 350 (e.g., relays 380).

Referring still to FIG. 3B, control device 350 is shown to includewireless controller 370 and RF transceiver 306 which may provide data tocircuit 310. Circuit 310 provides data or control signals to powerrelays 380. Sensor circuit 372 includes sensor logic module 374, sensormemory 376, and sensor interface 378. Wireless controller 370 isconfigured to cause one or more lamps of the fluorescent lightingfixture to turn on and off via control signals sent to power relays 380.Wireless controller 370 can make a determination that an “on” or “off”signal should be sent to power relays 380 based on inputs received fromsensor circuit 372 or RF transceiver 306. For example, a command to turnthe lighting fixture “off” may be received at RF transceiver 306 andinterpreted by wireless controller 370. Upon recognizing the “off”command, wireless controller 370 provides an appropriate control signalto sensor circuit 372 which causes a switch of one or more of powerrelays 380 off. Similarly, when sensor 308 experiences an environmentalcondition, sensor logic module 374 may determine whether or not wirelesscontroller 370 should change “on/off” states. For example, if a highambient lighting level is detected by sensor 308, sensor logic module374 may determine that wireless controller 370 should change states suchthat power relays 380 are “off” Conversely, if a low ambient lightinglevel is detected by sensor 308, sensor logic module 374 may causewireless controller 370 to turn power relays 380 “on.” Other controldecisions, logic and activities provided by control device 350 and thecomponents thereof are described below and with reference to otherFigures.

When or after control decisions based on sensor 308 or commands receivedat RF transceiver 306 are made, in some exemplary embodiments, sensorlogic module 374 is configured to log usage information for the lightingfixture in sensor memory 376. For example, if wireless controller 370causes power relays 380 to change states such that the lighting fixtureturns on or off, wireless controller 370 may inform sensor logic module374 of the state change and sensor logic module 374 may log usageinformation based on the information from wireless controller 370. Theform of the logged usage information can vary for different embodiments.For example, in some embodiments, the logged usage information includesan event identifier (e.g., “on”, “off”, cause for the state change,etc.) and a timestamp (e.g., day and time) from which total usage may bederived. In other embodiments, the total “on” time for the lightingfixture (or lamp set) is counted such that only an absolute number ofhours that the lamp has been on (for whatever reason) has been trackedand stored as the logged usage information. In addition to logging oraggregating temporal values, each sensor logic module 374 may beconfigured to process usage information or transform usage informationinto other values or information. For example, in some embodimentstime-of-use information is transformed by sensor logic module 374 totrack the energy used by the lighting fixture (e.g., based on bulbratings, known energy draw of the fixture in different on/off/partial onmodes, etc.). In some embodiments, each sensor logic module 374 willalso track how much energy savings the lighting fixture is achievingrelative to a conventional lighting fixture, conventional control logic,or relative to another difference or change of the lighting fixture. Forthe purposes of many embodiments of this disclosure, any suchinformation relating to usage for the lighting fixture may be consideredlogged “usage information.” In other embodiments, the usage informationlogged by sensor logic module 374 is limited to on/off events ortemporal aggregation of on states; in such embodiments energy savingscalculations or other calculations may be completed by a mastercontroller 302 or another remote device.

In an exemplary embodiment, control device 350 (e.g., via wirelesstransceiver 306) is configured to transmit the logged usage informationto remote devices such as master controller 302. Wireless controller 370may be configured to recall the logged usage information from sensormemory 376 at periodic intervals (e.g., every hour, once a day, twice aday, etc.) and to provide the logged usage information to RF transceiver306 at the periodic intervals for transmission back to master controller302. In other embodiments, master controller 302 (or another networkdevice) transmits a request for the logged information to RF transceiver306 and the request is responded to by wireless controller 370 bytransmitting back the logged usage information. In a preferredembodiment a plurality of controllers such as control device 350asynchronously collect usage information for their fixture and mastercontroller 302, via request or via periodic transmission of theinformation by the controllers, gathers the usage information for lateruse.

Wireless controller 370 may also be configured to handle situations orevents such as transmission failures, reception failures, and the like.Wireless controller 370 may respond to such failures by, for example,operating according to a retransmission scheme or another transmitfailure mitigation scheme. Wireless controller 370 may also control anyother modulating, demodulating, coding, decoding, routing, or otheractivities of RF transceiver 306. For example, control device 350'scontrol logic (e.g., controlled by sensor logic module 374 and/orwireless controller 370) may periodically include making transmissionsto other controllers in a zone, making transmissions to particularcontrollers, or otherwise. Such transmissions can be controlled bywireless controller 370 and such control may include, for example,maintaining a token-based transmission system, synchronizing clocks ofthe various RF transceivers or controllers, operating under a slot-basedtransmission/reception protocol, or otherwise.

Referring still to FIG. 3B, sensor 308 may be an infrared sensor, anoptical sensor, a camera, a temperature sensor, a photodiode, a carbondioxide sensor, or any other sensor configured to sense environmentalconditions such as a lighting level or human occupancy of a space. Forexample, in one exemplary embodiment, sensor 308 is a motion sensor andsensor logic module 374 is configured to determine whether wirelesscontroller 370 should change states (e.g., change the state of powerrelays 380) based on whether motion is detected by sensor 308 (e.g.,detected motion reaches or exceeds threshold value). In the same orother embodiments, sensor logic module 374 may be configured to use thesignal from the sensor 308 to determine an ambient lighting level.Sensor logic module 374 may then determine whether to change statesbased on the ambient lighting level. For example, sensor logic module374 may use a condition such as time of day in addition to ambientlighting level to determine whether to turn the lighting fixture off oron. During a critical time of the day (e.g., while motion is present inthe area, during a scheduled evening event, during morning hours near aschool, etc.), even if the ambient lighting level is high, sensor logicmodule 374 may refrain from turning the lighting fixture off. In anotherembodiment, by way of further example, sensor logic module 374 isconfigured to provide a command to wireless controller 370 that isconfigured to cause wireless controller 370 to turn the one or morelamps of the fluorescent lighting fixture on when sensor logic module374 detects motion via the signal from sensor 308 and when sensor logicmodule 374 determines that the ambient lighting level is below athreshold setpoint.

Referring yet further to FIG. 3B, wireless controller 370 is configuredto prevent damage to lamps 340, 342 from manual or automatic controlactivities. Particularly, wireless controller 370 may be configured toprevent on/off cycling of lamps 340, 342 by holding the lamps in an “on”state for a predefined period of time (e.g., thirty minutes, fifteenminutes, etc.) even after the condition that caused the lamp to turn onis no longer true. Accordingly, if, for example, a low ambient lightinglevel causes circuit 310 to turn lamps 340, 342 on but then the ambientlighting level suddenly increases (the sun comes out), wirelesscontroller 370 may keep the lamps on (even though the on conditionexpired) for a predetermined period of time so that the lamps are takenthrough their preferred cycle. Similarly, wireless controller 370 may beconfigured to hold the lamp in an “off” state for a predefined period oftime since the lamp was last turned off to ensure that the lamp is giventime to cool or otherwise settle after the last “on” state.

Referring yet further to FIG. 3B, sensor logic module 374 or wirelesscontroller 370 may be configured to include a restrike violation module(e.g., in sensor memory 376) that is configured to prevent sensor logicmodule 374 from commanding circuit 310 to cause the fluorescent lamps toturn on while a restrike time is counted down. The restrike time maycorrespond with a maximum cool-down time for the lamp—allowing the lampto experience its preferred strike-up cycle even if a command to turnthe lamp back on is received at RF transceiver 306. In otherembodiments, sensor logic module 374 or wireless controller 370 may beconfigured to prevent rapid on/off switching due to sensed motion,another environmental condition, or a sensor or controller error. Sensorlogic module 374 or wireless controller 370 may be configured to, forexample, entirely discontinue the on/off switching based on inputsreceived from the sensor by analyzing the behavior of the sensor, theswitching, and logged usage information. By way of further example,sensor logic module 374 or wireless controller 370 may be configured todiscontinue the on/off switching based on a determination that switchingbased on the inputs from the sensor has occurred too frequently (e.g.,exceeding a threshold number of “on” switches within a predeterminedamount of time, undesired switching based on the time of day or night,etc.). Sensor logic module 374 or wireless controller 370 may beconfigured to log or communicate such a determination. Using suchconfigurations, sensor logic module 374 and/or wireless controller 370are configured to self-diagnose and correct undesirable behavior thatwould otherwise continue occurring based on the default, user, orsystem-configured settings.

According to one embodiment, a self-diagnostic feature would monitor thenumber of times that a fixture or device was instructed to turn on (oroff) based upon a signal received from a sensor (e.g. motion, ambientlight level, etc.). If the number of instructions to turn on (or off)exceeded a predetermined limit during a predetermined time period,sensor logic module 374 and/or wireless controller 370 could beprogrammed to detect that the particular application for the fixture ordevice is not well-suited to control by such a sensor (e.g. not anoptimum application for motion control or ambient light-based control,etc.), and would be programmed to disable such a motion or ambient lightbased control scheme, and report/log this action and the basis. Forexample, if the algorithm is based on more than X instructions to turnon (or off) in a 24 hour period, and the number of instructions providedbased on signals from the sensor exceeds this limit within this period,the particular sensor-based control function would be disabled, as notbeing optimally suited to the application and a notification would belogged and provided to a user or facility manager. Of course, the limitand time period may be any suitable number and duration intended to suitthe operational characteristics of the fixture/device and theapplication. In the event that a particular sensor-based control schemein a particular zone is disabled by the logic module and/or controlcircuit, the fixture or device is intended to remain operational inresponse to other available control schemes (e.g. other sensors,time-based, user input or demand, etc.). The data logged by sensor logicmodule 374 and/or wireless controller 370 may also be used in a‘learning capacity’ so that the controls may be more optimally tuned forthe fixtures/devices in a particular application and/or zone. Forexample, sensor logic module 374 and/or wireless controller 370 maydetermine that disablement of a particular sensor-based control featureoccurred due to an excessive number of instructions to turn on (or off)based on signals from a particular sensor that occurred within aparticular time window, and may be reprogrammed to establish analternate monitoring duration that excludes this particular time windowfor the particular sensor-based control scheme to ‘avoid’ time periodsthat are determined to be problematic. This ability to learn orself-update is intended to permit the system to adjust itself to updatethe sensor-based control schemes to different time periods that are moreoptimally suited for such a control scheme, and to avoid time periodsthat are less optimum for such a particular sensor-based control scheme.

Referring now to FIG. 4A, a flow chart of a process 400 for illuminatinga system of outdoor lighting fixtures is shown, according to anexemplary embodiment. Process 400 includes operating a first lightingfixture in a dimmed state of operation (step 402). An indication ofmotion from a first sensor at a first control circuit is then received(step 404). The first sensor and the first control circuit areassociated with the first lighting fixture. Using the first controlcircuit, the first lighting fixture is caused to change from a dimmedstate of operation to a fully illuminated state of operation (step 406).A first radio frequency transceiver of the first control circuit is thenused to transmit a data message indicating motion or a command toilluminate (step 408). The transmission is provided to other lightingfixtures (e.g., a subsequent lighting fixture in the same zone as thefirst lighting fixture).

Using the first control circuit, a timer is started (step 410). Thetimer may continue to run while the first lighting fixture is held in afully illuminated state (step 412). Process 400 includes checking forwhether another indication of motion has been received at the firstcontrol circuit (step 414). The indication of motion may be receivedfrom the first sensor according to an exemplary embodiment. If anindication of motion has been received, the first control circuitrestarts the timer (step 410).

Process 400 includes checking for whether a command to fully illuminatehas been received at a first control circuit from a remote source (step416). The remote source may include another lighting fixture, accordingto an exemplary embodiment. If a command to fully illuminate has beenreceived, the first control circuit restarts the timer (step 410). If noindication of motion or command from a remote source has been received,process 400 includes checking for whether time has elapsed (step 418).If the time has not elapsed, the timer continues to run (e.g., count up,count down, etc.) and the first lighting fixture remains in anilluminated state (step 412). If the time has elapsed, the firstlighting fixture changes to a dimmed state of operation (step 402).

Referring now to FIG. 4B, a flow chart of a process 450 for using motioninformation to change states of a system of outdoor lighting fixtures isshown, according to an exemplary embodiment. Process 450 includesreceiving motion information from a remote sensor of a remote lightingfixture at a local lighting fixture (step 452). Motion information mayinclude information about a moving object (e.g., a vehicle) such as thelocation of the vehicle when detected, a lighting fixture identifier, azone identifier, or a lighting fixture location and a timestampassociated with the motion detection. Step 452 may further includereceiving motion information about the same vehicle (or other movingobject) from additional motion sensors coupled to additional lightingfixtures. Process 450 further includes receiving motion information froma local sensor of the lighting fixture (step 454). The motioninformation from the local sensor may be transmitted to a remotelighting fixture (step 456). According to one exemplary embodiment,process 450 may be executed at one lighting fixture and the results ofprocess 450 may be transmitted to all other lighting fixtures. Accordingto other exemplary embodiments, steps 452-456 may be executed atmultiple lighting fixtures, allowing one or more other lighting fixturesto execute process 450 and to transmit the results to each other.

The timestamps associated with each set of motion information receivedmay be recorded (step 458). A speed or direction of the detected vehicleis then calculated based on the motion information (step 460). Step 460may include using the timestamps of the motion information along withlocation information of the sensors capturing the motion information todetermine a speed at which the detected vehicle was traveling along withthe direction in which the detected vehicle was traveling. Step 460 mayfurther include estimating the current location of the vehicle.

The vehicle information (e.g., speed, direction, etc.) is used todetermine which zones and lighting fixtures the vehicle may travelthrough next (step 462). The determination may be based on vehicle speed(e.g., the faster the vehicle is traveling, the more zones and lightingfixtures are affected as the vehicle will be approaching them quicker),vehicle direction (e.g., on a road with no turns, all zones or lightingfixtures under which the vehicle must travel before reaching a turn maybe affected), and vehicle location (e.g., all zones or lighting fixtureswithin a specific distance of the current vehicle location may bedetermined to be affected by the vehicle motion). Process 450 furtherincludes using the motion information to determine whether or not tochange the state of the local lighting fixture (step 464). Process 450further includes transmitting a command to illuminate (or to otherwisechange states) to the affected zones and lighting fixtures (step 466).For example, affected zones and lighting fixtures may include thelighting fixture closest to the local lighting fixture, the nextlighting fixture from the local lighting fixture, all lighting fixturesin the same zone as the local lighting fixture, the zones surroundingthe local lighting fixture, or otherwise. For example, if a vehicle isestimated to travel through a zone, all lighting fixtures within thezone may receive a command to change to an “on” state. As anotherexample, only specific lighting fixtures under which the vehicle isexpected to travel under may receive a command to change to an “on”state. In some embodiments the lighting fixture will transmit “on”commands to lighting fixtures at a rate proportionate to the speed atwhich the vehicle is traveling. Accordingly, a greater number oflighting fixtures ahead of the vehicle may be commanded to be turned onfor vehicles traveling at a great rate of speed relative to slowervehicles.

According to an exemplary embodiment, the change in states in steps 464,466 may include changing from a fully illuminated state to a dimmedstate, from a dimmed state to a fully illuminated state, from an offstate to an illuminated or dimmed state, or otherwise. The changing ofstates may include configuring the lighting fixtures such that a “movingwindow” may be created (e.g., creating a succession of state changessuch that lighting fixtures directly surrounding a vehicle are alwaysfully illuminated while the next closest lighting fixtures are in adimmed state) or configuring the lights in another manner (e.g., lightsthat are off may change to a dimmed state if the vehicle is approachingor if the vehicle just drove away from the area illuminated by thelight, etc.).

According to an alternative exemplary embodiment, process 450 may beexecuted at a remote controller. The remote controller may receivemotion information from all lighting fixtures and determine whichlighting fixtures should change states. The remote controller may thentransmit the command to the system of lighting fixtures.

Referring now to FIG. 5A, a more detailed block diagram of mastercontroller 302 (e.g., a control computer) is shown, according to anexemplary embodiment. Master controller 302 may be configured as the“master controller” described in U.S. application Ser. No. 12/240,805,filed Sep. 29, 2008, and incorporated herein by reference in itsentirety. Master controller 302 is generally configured to receive userinputs (e.g., via touchscreen display 530) and to set or change settingsof the lighting system based on the user inputs.

Referring further to FIG. 5A, master controller 302 is shown to includeprocessing circuit 502 including memory 504 and processor 506. In anexemplary embodiment, master controller 302 and more particularlyprocessing circuit 502 are configured to run a Microsoft WindowsOperating System (e.g., XP, Vista, etc.) and are configured to include asoftware suite configured to provide the features described herein. Thesoftware suite may include a variety of modules (e.g., modules 508-514)configured to complete various activities of master controller 302.Modules 508-514 may be or include computer code, analog circuitry, oneor more integrated circuits, or another collection of logic circuitry.In various exemplary embodiments, processor 506 may be a general purposeprocessor, a specific purpose processor, a programmable logic controller(PLC), a field programmable gate array, a combination thereof, orotherwise and configured to complete, cause the completion of, and/orfacilitate the completion of the activities of master controller 302described herein. Memory 504 may be configured to store historical datareceived from lighting fixture controllers or other devices,configuration information, schedule information, setting information,zone information, or other temporary or archived information. Memory 504may also be configured to store computer code for execution by processor506. When executed, such computer code (e.g., stored in memory 504 orotherwise, script code, object code, etc.) configures processing circuit502, processor 506 or more generally master controller 302 for theactivities described herein.

Touch screen display 530 and more particularly user interface module 508are configured to allow and facilitate user interaction (e.g., input andoutput) with master controller 302. It should be appreciated that inalternative embodiments of master controller 302, the display associatedwith master controller 302 may not be a touch screen, may be separatedfrom the casing housing master controller 302, and/or may be distributedfrom master controller 302 and connected via a network connection (e.g.,Internet connection, LAN connection, WAN connection, etc.). Further, itshould be appreciated that master controller 302 may be connected to amouse, keyboard, or any other input device or devices for providing userinput to master controller 302. Master controller 302 is shown toinclude a communications interface 532 configured to connect to a wireassociated with master transceiver 304.

Communications interface 532 may be a proprietary circuit forcommunicating with master transceiver 304 via a proprietarycommunications protocol. In other embodiments, communications interface532 may be configured to communicate with master transceiver 304 via astandard communications protocol. For example, communications interface532 may include Ethernet communications electronics (e.g., an Ethernetcard) and an appropriate port (e.g., an RJ45 port configured for CAT5cabling) to which an Ethernet cable is run from master controller 302 tomaster transceiver 304. Master transceiver 304 may be as described inU.S. application Ser. Nos. 12/240,805, 12/057,217, or 11/771,317 whichare each incorporated herein by reference. Communications interface 532and more generally master transceiver 304 are controlled by logic ofwireless interface module 512. Wireless interface module 512 may includedrivers, control software, configuration software, or other logicconfigured to facilitate communications activities of master controller302 with lighting fixture controllers. For example, wireless interfacemodule 512 may package, address format, or otherwise prepare messagesfor transmission to and reception by particular controllers or zones.Wireless interface module 512 may also interpret, route, decode, orotherwise handle communications received at master transceiver 304 andcommunications interface 532.

Referring still to FIG. 5A, user interface module 508 may include thesoftware and other resources for the display and the handling ofautomatic or user inputs received at the graphical user interfaces ofmaster controller 302. While user interface module 508 is executing andreceiving user input, user interface module 508 may interpret user inputand cause various other modules, algorithms, routines, or sub-processesto be called, initiated, or otherwise affected. For example, controllogic module 514 and/or a plurality of control sub-processes thereof maybe called by user interface module 508 upon receiving certain user inputevents. User interface module 508 may also be configured to includeserver software (e.g., web server software, remote desktop software,etc.) configured to allow remote access to the display. User interfacemodule 508 may be configured to complete some of the control activitiesdescribed herein rather than control logic module 514. In otherembodiments, user interface module 508 merely drives the graphical userinterfaces and handles user input/output events while control logicmodule 514 controls the majority of the actual control logic.

Control logic module 514 may be the primary logic module for mastercontroller 302 and may be the main routine that calls, for example,modules 508, 510, etc. Control logic module 514 may generally beconfigured to provide lighting control, energy savings calculations,demand/response-based control, load shedding, load submetering, HVACcontrol, building automation control, workstation control, advertisementcontrol, power strip control, “sleep mode” control, or any other typesof control. In an exemplary embodiment, control logic module 514operates based off of information stored in one or more databases ofmaster controller 302 and stored in memory 504 or another memory devicein communication with master controller 302. The database may bepopulated with information based on user input received at graphicaluser interfaces and control logic module 514 may continuously draw onthe database information to make control decisions. For example, a usermay establish any number of zones, set schedules for each zone, createambient lighting parameters for each zone or fixture, etc. Thisinformation is stored in the database, related (e.g., via a relationaldatabase scheme, XML sets for zones or fixtures, or otherwise) andrecalled by control logic module 514 as control logic module 514proceeds through its various control algorithms.

Control logic module 514 may include any number of functions orsub-processes. For example, a scheduling sub-process of control logicmodule 514 may check at regular intervals to determine if an event isscheduled to take place. When events are determined to take place, thescheduling sub-process or another routine of control logic module 514may call or otherwise use another module or routine to initiate theevent. For example, if the schedule indicates that a zone should beturned off at 5:00 pm, then when 5:00 pm arrives the schedulingsub-process may call a routine (e.g., of wireless interface module) thatcauses an “off” signal to be transmitted by master transceiver 304.Control logic module 514 may also be configured to conduct or facilitatethe completion of any other process, sub-process, or process stepsconducted by master controller 302 described herein. For example,control logic module 514 may be configured to use motion informationreceived from remote sensors and determine a state for the lightingfixture and other lighting fixtures.

Referring further to FIG. 5A, device interface module 510 facilitatesthe connection of one or more field devices, sensors, or other inputsnot associated with master transceiver 304. For example, fieldbusinterfaces 516, 520 may be configured to communicate with any number ofmonitored devices 518, 522. The communication may be according to acommunications protocol which may be standard or proprietary and/orserial or parallel. Fieldbus interfaces 516, 520 can be or includecircuit cards for connection to processing circuit 502, jacks orterminals for physically receiving connectors from wires couplingmonitored devices 518, 522, logic circuitry or software for translatingcommunications between processing circuit 502 and monitored devices 518,522, or otherwise. In an exemplary embodiment, device interface module510 handles and interprets data input from the monitored devices andcontrols the output activities of fieldbus interfaces 516, 520 tomonitored devices 518, 522.

Fieldbus interfaces 516, 520 and device interface module 510 may also beused in concert with user interface module 508 and control logic module514 to provide control to the monitored devices 518, 522. For example,monitored devices 518, 522 may be mechanical devices configured tooperate a motor, one or more electronic valves, one or moreworkstations, machinery stations, a solenoid or valve, or otherwise.Such devices may be assigned to zones similar to the lighting fixturesdescribed above and below or controlled independently. User interfacemodule 508 may allow schedules and conditions to be established for eachof devices 518, 522 so that master controller 302 may be used as acomprehensive energy management system for a facility. For example, amotor that controls the movement of a spinning advertisement may becoupled to the power output or relays of a controller very similar ifnot identical to master controller 302. This controller may be assignedto a zone (e.g., via user interfaces at touchscreen display 530) andprovided a schedule for turning on and off during the day. In anotherembodiment, the electrical relays of the controller may be coupled toother devices such as video monitors for informational display, exteriorsigns, task lighting, audio systems, or other electrically operateddevices.

Referring further to FIG. 5A, power monitor 550 is shown as coupled tofieldbus interfaces 516 in an exemplary embodiment. However, powermonitor 550 may also or alternatively be coupled to its own controlleror RF transceiver 551 for communicating with master transceiver 304.Power monitor 550 may generally be configured to couple to powerresources (e.g., facility outputs, power company transformers, buildingmains input, building power meter, etc.) and to receive or calculate anindication of power utilized by a facility or lighting system. Thisinput may be received in a variety of different ways according tovarying embodiments. For example, power monitor 550 may include acurrent transformer (CT) configured to measure the current in the mainsinlet to a lighting system or facility, may be coupled to or include apulse monitor, may be configured to monitor voltage, or may monitorpower in other ways. Power monitor 550 is intended to provide “realtime” or “near real time” monitoring of power and to provide the resultof such monitoring to master controller 302 for use or reporting. Whenused with power monitor 550, control logic module 514 may be configuredto include logic that sheds loads (e.g., sends off signals to lightingfixtures via a lighting fixture controller network, sends off signals tomonitored devices 518, 522, adjusts ambient light setpoints, adjustsschedules, shuts lights off according to a priority tier, etc.) tomaintain a setpoint power meter level or threshold. In other exemplaryembodiments, control logic module 514 may store or receive pricinginformation from a utility and shed loads if the metered power usagemultiplied by the pricing rate is greater than certain absolutethresholds or tiered thresholds. For example, if daily energy cost isexpected to exceed $500 for a facility or lighting system, control logicmodule 506 may be configured to change the ambient light setpoints forthe lighting fixtures in the system until daily energy cost is expectedto fall beneath $500. In an exemplary embodiment, user interface module508 is configured to cause a screen to be displayed that allows a userto associate different zones or lighting fixtures with differentdemand/response priority levels. Accordingly, a utility provider orinternal calculation determines that a load should be shed, controllogic module 514 will check the zone or lighting fixture database toshed loads of the lowest priority first while leaving higher priorityloads unaffected.

Referring now to FIG. 5B, a diagram of a facility lighting system 560for use with the lighting fixture system including controller 302 isshown, according to an exemplary embodiment. Master controller 302(e.g., a control computer) is preferably configured to provide agraphical user interface to a local or remote electronic display screenfor allowing a user to adjust control parameters, turn lighting fixtureson or off, or to otherwise affect the operation of lighting fixtures ina facility. For example, master controller 302 is further shown toinclude touch screen display 530 for displaying such a graphical userinterface and for allowing user interaction (e.g., input and output)with master controller 302. Various exemplary graphical user interfacesfor display on touch screen display 530 and control activitiesassociated therewith are described in subsequent paragraphs and withreference to subsequent Figures of the present disclosure. It should benoted that while master controller 302 is shown in FIG. 5B as housed ina wall-mounted panel it may be housed in or coupled to any othersuitable computer casing or frame. The user interfaces are intended toprovide an easily configurable lighting and/or energy management systemfor a facility. The user interfaces are intended to allow even untrainedusers to reconfigure or reset a lighting system using relatively fewclicks. In an exemplary embodiment, the user interfaces do not require akeyboard for entering values. Advantageously, users other than engineersor facility managers may be able to setup, interact with, or reconfigurethe system using the provided user interfaces.

Referring further to FIG. 5B, master controller 302 is shown connectedto master transceiver 304. Master transceiver 304 may be a radiofrequency transceiver configured to provide wireless signals to anetwork of controllers such as master controller 302. In FIG. 5B, mastertransceiver 304 is shown in bi-directional wireless communication with aplurality of lighting fixtures 12, 14, 18, 20. FIG. 5B furtherillustrates fixtures 12, 14 forming a first logical group 102 identifiedas “Zone I” and fixtures 18, 20 forming a second logical group 104identified as “Zone II” (e.g., the zones 102, 104 as shown in FIG. 2).

Master controller 302 may be configured to provide commands for zones102, 104 and their associated lighting fixtures. For example, alsoreferring to FIG. 4B, master controller 302 may receive motioninformation from the sensors of lighting fixtures 12, 14, 18, 20 andprovide commands for lighting fixtures 12, 14, 18, 20 to mastertransceiver 304 for transmitting to the appropriate zones and lightingfixtures. Master controller 302 may be configured to provide differentprocessing or different commands for zone 102 relative to zone 104. Forexample, a command to change a lighting fixture status may betransmitted to only zone 102 if master controller 302 determines onlyzone 102 is affected by a current condition (e.g., a detected vehicle,etc.) While master controller 302 is configured to complete a variety ofcontrol activities for lighting fixtures 12, 14, 18, 20, in manyexemplary embodiments of the present disclosure, each controllerassociated with a lighting fixture (e.g., lighting fixtures 12, 14, 18,20) includes circuitry configured to provide a variety of “smart” or“intelligent features” that are either independent of master controller302 or operate in concert with master controller 302.

According to various exemplary embodiments, the systems and methods ofthe present disclosure may be used in a street lighting system.According to other exemplary embodiments, the systems and methods of thepresent disclosure may be used in warehouses, parking lots, garages, orotherwise. For example, the lighting system can be used in a gas station(e.g., when a vehicle approaches a pump, pump lights or canopy lightscan turn on or change to a brightened state, a camera may be caused toactivate, and a control circuit within the pump may be communicated withto trigger the playback of advertisements via a pump display and/or viaa pump audio system, etc.).

While many of the embodiments described herein utilize activecommunication (e.g., RF commands, RF information messages, etc.) toeffect the serial illumination of a plurality of outdoor lightingfixtures, in other embodiments the lighting fixtures of an outdoorlighting system only utilize local sensor information (e.g., motionsensor, light sensor, infrared sensor, etc.) to determine whether toilluminate. In such embodiments, a radio frequency transceiver or otherelectronics for fixture-to-fixture communications may not be provided.In yet other embodiments, the radio frequency transceiver or otherelectronics for fixture-to-fixture communications are provided but arenot utilized by circuitry of the outdoor lighting system for respondingto environmental states (e.g., motion, presence of a vehicle, etc.).

In an embodiment where the lighting fixtures do not utilize activecommunication (e.g., RF commands, RF information messages, etc.) toeffect the serial illumination of a plurality of outdoor lightingfixtures, each outdoor lighting fixture includes a control circuit andan environment sensor. The control circuit only illuminates the outdoorlighting fixture in response to manual triggering, a pre-establishedschedule, a command signal from a supervisory controller, or a sensorsignal (e.g., that there is motion detected nearby). The control circuitoperates the lighting fixture without recognizing any fixture-to-fixturecommunications.

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although only afew embodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements may bereversed or otherwise varied and the nature or number of discreteelements or positions may be altered or varied. Accordingly, all suchmodifications are intended to be included within the scope of thepresent disclosure. The order or sequence of any process or method stepsmay be varied or re-sequenced according to alternative embodiments.Other substitutions, modifications, changes, and omissions may be madein the design, operating conditions and arrangement of the exemplaryembodiments without departing from the scope of the present disclosure.For example, the lighting fixtures described herein may be used withvarying bulb technologies (e.g., high intensity discharge (HID), highintensity fluorescent (HIF), LED, etc.) according to varying exemplaryor alternative embodiments.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Combinationsof the above are also included within the scope of machine-readablemedia. Machine-executable instructions include, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions.

Although the figures may show a specific order of method steps, theorder of the steps may differ from what is depicted. Also two or moresteps may be performed concurrently or with partial concurrence. Suchvariation will depend on the software and hardware systems chosen and ondesigner choice. All such variations are within the scope of thedisclosure. Likewise, software implementations could be accomplishedwith standard programming techniques with rule based logic and otherlogic to accomplish the various connection steps, processing steps,comparison steps and decision steps.

What is claimed is:
 1. A lighting fixture, comprising: a first light anda second light; a motion sensor; a radio frequency transceiver; and acircuit coupled to the first light, the second light, the motion sensor,and the radio frequency transceiver; wherein the circuit is configuredto cause the first light to be in an activated state of operation suchthat the first light is illuminating and the second light to be in adeactivated state of operation such that the second light is notilluminated; wherein the circuit is further configured to receive asignal from the motion sensor and to determine whether the signal isrepresentative of motion; wherein the circuit is further configured torespond to a determination that the signal is representative of motionby causing the second light to enter an activated state of operationsuch that the second light is illuminated; wherein the circuit isfurther configured to cause the radio frequency transceiver to transmitat least one of a message indicating motion and an illuminate commandfor receipt by other lighting fixtures.
 2. The lighting fixture of claim1, wherein the lighting fixture is further configured to respond to atransmission received from other lighting fixtures at the radiofrequency transceiver, and to activate the second light if thetransmission is a message indicating motion or an illuminate command. 3.The lighting fixture of claim 2, wherein the lighting fixture is furtherconfigured to retransmit, via the radio frequency transceiver, thereceived transmission as an indication of motion or an illuminatecommand in response to receiving the transmission.
 4. The lightingfixture of claim 3, wherein the circuit is configured to deactivate thesecond light after a period of time wherein no new radio frequencytransmissions are received and no new motion is detected via the motionsensor, and wherein the circuit is configured to hold the first lightingfixture in an activated state despite the deactivation of the secondlight.
 5. The lighting fixture of claim 4, wherein the circuit isconfigured to cause status information to be transmitted, via the radiofrequency transceiver, to nearby lighting fixtures for retransmission toa main controller.
 6. The lighting fixture of claim 5, wherein thecircuit is configured to only react to received radio frequencytransmissions if received from a lighting fixture of its zone or anadjacent zone.
 7. The lighting fixture of claim 6, wherein the lightingfixture is a streetlight.
 8. The lighting fixture of claim 7, whereinthe motion sensor and the circuit are configured to ascertain adirection of movement in addition to the binary presence or absence ofmotion, and to adjust at least one lighting event in response to theascertained direction of movement.
 9. The lighting fixture of claim 8,wherein the motion sensor and the circuit are configured to ascertain aspeed of movement in addition to the binary presence or absence ofmotion, and to adjust the at least one lighting event in response to theascertained speed of the movement.
 10. The lighting fixture of claim 9,wherein the first light is a high intensity discharge fluorescent lamp.11. The lighting fixture of claim 9, wherein the second light is a highintensity discharge fluorescent lamp.
 12. The lighting fixture of claim9, wherein the first lamp and the second lamp are LED arrays.